Release 10.1A: OpenEdge Data Management:
DataServer for ODBC

DataServer components

The DataServer for ODBC can run in a variety of configurations. Some configurations involve a single process running on one machine. Others involve multiple processes running on different machines across multiple platforms.

Before you configure a DataServer, you must register your data source as an ODBC data source. For details, see the "Registering your data source" section.

To set up a DataServer configuration, determine which components you need on which platforms, then set up the appropriate executables on those platforms. Table 3–1 lists the possible combinations and describes which executables you must set up on each machine. In this table, the term local indicates that the DataServer component runs on the same machine as the client, while the term remote indicates that the component runs on a different machine than the client.

Table 3–1: Installing the DataServer components 

Client	DataServer	Installing and configuring
Windows	Local Windows	Use the default OpenEdge client executable (prowin32.exe). The server component is embedded in the client executable.
Windows	Remote Windows	On the client machine, use the default OpenEdge client executable (prowin32.exe). On the host machine, use the default broker executable (_probrkr.exe) or configure a broker executable using the Progress Explorer.
UNIX	Remote Windows	On the client machine, use the OpenEdge client executable (_progres). On the host machine, use the default broker executable (_probrkr.exe) or configure a broker using the Progress Explorer.

For instructions on setting up your DataServer configuration, see the sections that apply to the platforms that you will use. For example, if you are configuring a local DataServer, see the "Configuring a local DataServer" section. If you are building a remote DataServer configuration host, see the "Configuring the remote DataServer" section.